Mobile communication system and method for processing handover procedure thereof

ABSTRACT

A method for processing a handover procedure in a mobile communication system is disclosed. After a type of handover is recognized based on information included in a handover command, a radio resource reconfiguration operation is selectively performed or a data transmission start point is adjusted, to thereby minimize an unnecessary operation occurring in the handover process and optimize a data transmission between a user equipment and a base station.

The present application claims the priority benefits of U.S. ProvisionalApplication No. 61/026,119 filed on Feb. 4, 2008 and Korean PatentApplication No. 10-2009-0008159 filed on Feb. 2, 2009 in Republic ofKorea. The entire contents of these applications are herein fullyincorporated by reference.

TECHNICAL FIELD

The present invention relates to a long term evolution (LTE) system and,more particularly, to a mobile communication system for differentlyperforming radio resource reconfiguration according to types ofhandover, and a method for processing a handover procedure thereof.

BACKGROUND ART

FIG. 1 shows a network structure of the E-UMTS, a mobile communicationsystem, applicable to the related art and the present invention. TheE-UMTS system has been evolved from the UMTS system, for which the 3GPPis proceeding with the preparation of the basic specifications. TheE-UMTS system may be classified as the LTE (Long Term Evolution) system.

The E-UMTS network may be divided into an evolved-UMTS terrestrial radioaccess network (E-UTRAN) and a core network (CN). The E-UTRAN includes aterminal (referred to as ‘UE (User Equipment), hereinafter), a basestation (referred to as an eNode B, hereinafter), a serving gateway(S-GW) located at a termination of a network and connected to anexternal network, and a mobility management entity (MME) superintendingmobility of the UE. One or more cells may exist for a single eNode B.

FIGS. 2 and 3 illustrate a radio interface protocol architecture basedon a 3GPP radio access network specification between the UE and the basestation. The radio interface protocol has horizontal layers comprising aphysical layer, a data link layer, and a network layer, and has verticalplanes comprising a user plane for transmitting data information and acontrol plane for transmitting control signals (signaling). The protocollayers can be divided into the first layer (L1), the second layer (L2),and the third layer (L3) based on three lower layers of an open systeminterconnection (OSI) standard model widely known in communicationsystems.

The radio protocol control plane in FIG. 2 and each layer of the radioprotocol user plane in FIG. 3 will now be described.

The physical layer, namely, the first layer (L1), provides aninformation transfer service to an upper layer by using a physicalchannel. The physical layer is connected to an upper layer called amedium access control (MAC) layer via a transport channel, and data istransferred between the MAC layer and the physical layer via thetransport channel. Meanwhile, between different physical layers, namely,between a physical layer of a transmitting side and that of a receivingside, data is transferred via a physical channel.

The MAC layer of the second layer provides a service to a radio linkcontrol (RLC) layer, its upper layer, via a logical channel. An RLClayer of the second layer may support reliable data transmissions. APDCP layer of the second layer performs a header compression function toreduce the size of a header of an IP packet including sizableunnecessary control information to thereby effectively transmit an IPpacket such as IPv4 or IPv6 in a radio interface with a relatively smallbandwidth.

A radio resource control (RRC) layer located at the lowest portion ofthe third layer is defined only in the control plane and handles thecontrolling of logical channels, transport channels and physicalchannels in relation to configuration, reconfiguration and release ofradio bearers (RBs). The radio bearer refers to a service provided bythe second layer (L2) for data transmission between the UE and theUTRAN.

A random access channel (RACH) will now be described. The RACH is usedto transmit data with a relatively short length to uplink, and inparticular, the RACH is used when a UE, which has not been allocateddedicated radio resources, has a signaling message or user data to betransmitted to uplink. Or, the RACH may be also used for a base stationto instruct a UE to perform a RACH procedure.

The mobile communication system is different from a fixed linecommunication system in that the mobile communication system shouldprovide a seamless service to UEs with mobility. Namely, the mobilecommunication system features that it supports the case where a UE movesto a different area. When the UE becomes away from a connected basestation and simultaneously becomes close to a different base station, anetwork should perform an operation of changing a connection point ofthe UE to the new base station from the serving base station. While theUE is disconnected from the old base station and completes itsconnection to the new base station, there is no data transmission orreception.

Meanwhile, every user data has a transmission limit time. For example,in case of a voice call, single voice information generated from adevice intending transmission of the voice information should betransmitted to a device that is to receive the voice information withina certain time. In addition, data such as TCP ( ) should be deliveredfrom a sender to a recipient within a certain time, and the receptionside should inform the sender about acknowledgement oftransmission/reception of the TCP data within a certain time, otherwisethe sender would re-transmit the TCP data.

In general, the UE and the base station continuously exchangetransmission/reception acknowledgement information with respect to thetransmitted/received data. For example, in case of a TCP packet, if asingle packet is lost by lower entities while being transmitted from thesender to the recipient, the transmission side TCP entity rapidly lowersa transmission rate (speed) of the TCP data. For example, thetransmission side TCP entity, which generates data and transmits thesame to the reception side at a rate of 100 Mbit/s, determines that thereception side has failed to receive even only one packet, thetransmission side TCP entity rapidly lowers the transmission rate of theTCP data to, for example, 10 Kbit/s.

Thus, in the mobile communication system, in order to reduce aninfluence on the TCP, a lossless mode to effectively support trafficsuch as the TCP between the base station and the UE. The lossless modemay be considered an AM (Acknowledge Mode) RLC, and if the transmissionside fails to receive a reception acknowledgement response with respectto its transmitted data from the reception side within a certain time orif the transmission side receives information of a reception failurewith respect to its transmitted data, the transmission side re-transmitsthe data.

In this case, however, when the transmission side receives theinformation of reception failure with respect to certain data, it doesnot always perform retransmission with respect to the corresponding databut performs retransmission only when a transmission/receptionacknowledgement response is made within a maximum transmission delaytime defined in a radio interface.

FIG. 4 is a signal flow chart illustrating a handover procedure betweenthe UE and the base station defined in the LTE.

As shown in FIG. 4, the UE performs measurement on the strength or thelike of signals with respect to each cell, and if a particular reference(base) designated by the base station is satisfied according to themeasurement results, the UE transmits a measurement report message to asource base station (source eNB) via uplink (UL) (S10).

The source eNB determines performing of handover to move the UE to acell of a target eNB with reference to the measurement report messagereceived from the UE, and transmits context data to the target eNB torequest preparation of handover (S20).

The target eNB secures radio resources under its management, andtransfers radio resource configuration information together with atemporary identifier (new C-RNTI) with respect to the corresponding UEto the source eNB. The source eNB transmits a handover command to the UE(S40) and then starts transmission of user data (PDCP SDU) or the liketo the target eNB. In this case, the source eNB transmits data (PDOPSOUs) which have been successively received from the UE to a corenetwork (MME/UPE), and transfers first one (PDCP SDU) of data which havenot been successively received from the UE, to the target eNB. Also, thesource eNB delivers data which have not been acknowledged by the UE,among the data (PDCP SDUs) the source eNB had transmitted to the UE.

Upon receiving the handover command, the UE reestablishes a radioenvironment with the target eNB including timing synchronization (S50).The target eNB response to the UE by timing information, and the UEtransmits a handover confirmation message to the target eNB (S60). Inthis case, the target eNB transmits reception acknowledgementinformation with respect to the handover confirmation message to the UE.Additionally, the target eNB may transmit user datatransmission/reception confirmation information (PDCP status report) tothe UE. The PDCP status report informs about which user data (PDCP SDUs)have been successfully received by the source eNB from the UE and aboutwhich user data (PDCP SDUs) have not been successfully received. Inother words, the PDCP status report may be interpreted as information ofuser data the target eNB requests its retransmission from the UE.

Upon receiving the PDCP status report, the UE retransmits data informedto have not been successfully received by the source eNB among the dataattempted to have been transmitted to the eNB, and does not retransmitdata informed to have been successfully received by the eNB.

Thereafter, when the handover is completed, the target eNB informs thesource eNB about the success of handover (S70), and transmits user datato the core network (MME/UPE) to update the location of the UE. At thistime, with respect to the user data which had been attempted to betransmitted by the UE when the UE located within the source eNB, thetarget eNB performs realigning on the user data received from the sourceeNB and the data received from the UE located within the target eNB, andtransfers successfully restored user data to the MME/UPE.

In the related handover procedure, as soon as the UE is connected to thenew target eNB, the UE starts transmission to the target eNB, startingfrom the first user data which had not been acknowledged by the sourceeNB, among the user data the UE had transmitted to the source eNB instep S60. Namely, the UE does not start user data transmission to uplinkafter it receives the user data transmission/reception confirmationinformation from the target as soon as the UE is connected to the newtarget eNB, but starts transmission to the uplink at the same time whenthe handover occurs. Such user data transmission causes a first problemas follows.

FIG. 5 shows an example of an unnecessary data transmission occurring inthe handover procedure between the UE and the base station.

With reference to FIG. 5, the transmission side PDCP entity of the UEstarts transmission of six user data (PDCP SDU 1 to PDCP SDU 6) to thetransmission side RLC at a time T0, and the transmission RLC entitytransmits user data by using RLC PDU 1 to RLC PDU 6. In this case, onlyRLC PDU 1, among the six RLC PDUs, is acknowledged by the reception sideRLC, while the RLC PDU 2 to RLC PDU 6 have been received by thereception side RLC but their status report has not been transmitted yet.The received RLC PDU 1 to RLC PDU 6 are delivered to an upper layer atthe reception side.

When handover occurs at the time T1, the transmission side and receptionside RLC entities are all reset, and the transmission side PDCP entitytransmits all the PDCP SDUs (PDCP SDU 2 to PDCP SDU 6) starting from thePDCP SDU 2, and the transmission side RLC entity transmits the user databy using RLC PDU A to RLC PDU G. At this time, the reception side PDCPentity transmits a PDCP status report to the transmission side PDCPentity.

At a time T2, namely, when the PDCP status report has not been receivedyet, the transmission side RLC entity exchanges the RLC PDUs with a peerentity (i.e., the reception side RLC entity).

Thereafter, when the PDCP status report arrives at the transmission sidePDCP entity at a time T3, the transmission side PDCP entity confirmsthat the PDCP SDU 1 to PDCP SDU 6 are all received by the receptionside, deletes the PDCP SDU 2 to PDCP SDU 6, and transmits discardindication information with respect to the discarded PDCP SDUs or thelike to the RLC entity.

In this manner, although the source eNB successfully receives the PDCPSDU 1 to PDCP SDU 6 at the time T0 to T1, unless an acknowledgement ofthe PDCP SDU 2 to PDCP SDU 6 is transferred to the UE, the UE startstransmission of the PDCP SDU 2 to PDCP SDU 6 in the new cell. In thiscase, because the UE starts transmission of the PDCP SDUs before itreceives the transmission/reception acknowledgement response from thetarget eNB, the unnecessary transmission is generated. In addition, theunnecessary retransmission of the data delays transmission of new data,negatively affecting the quality of service (QoS) of the system.

SUMMARY OF THE INVENTION

The handover operations in the related art are performed by the terms ofthe source base station and the target base station, which, however, isalways performed regardless of the types of handover. Namely, it occursalthough the source base station and the target base station are thesame.

In case where the source base station and the target base station aredifferent, such operations may be considered to be optimum because datatransmission should be necessarily performed, but when the source basestation and the target base station are the same, the above-mentionedoperations include many unnecessary factors.

For example, when the source base station and the target base stationare the same, there is no need to forward data, namely, there is no needto transfer the user data from one base station to another base station.In addition, when the source base station and the target base stationare the same, the same RLC entity and PDCP entity can be used before andafter handover.

Nonetheless, the current handover operation does not discriminatehandover in the same base station and handover between different basestations.

Therefore, in order to address the above matters, the various featuresdescribed herein have been conceived. One aspect of the exemplaryembodiments is to provide a mobile communication system and a method forprocessing a handover procedure, capable of optimizing data transmissionbetween a UE and a base station by minimizing an unnecessary operationin the handover process

This specification provides a method for processing a handover procedureof a mobile communication system, including: receiving a radio resourcereconfiguration message from a base station; recognizing a handover typebased on information included in the received radio resourcereconfiguration message; and performing a first or second handoverprocedure according to the recognized handover type.

The radio resource reconfiguration message may be a handover command.

The information may include a C-RNT, a handover type indicator, aphysical cell identity (PCI), and a reconfiguration indicator. Thereconfiguration indicator may include a reconfiguration indicator of anRLC entity and that of a PDCP entity.

The first handover procedure may indicate a procedure for handoverbetween different base stations (intra Node B HO), and the secondhandover procedure may indicate a procedure for handover in the samebase station (inter Node B HO).

The method may further include: if a transmission/receptionacknowledgement information operation indicator is included in theinformation, starting data transmission after receivingtransmission/reception acknowledgement information. Thetransmission/reception acknowledgement information may be a PDCP statusPDU.

This specification also provides a mobile communication systemincluding: a base station that transmits a radio resourcereconfiguration message; and a user equipment (mobile terminal) thatrecognizes a handover type based on information included in a receivedradio resource reconfiguration message and performs a first or secondhandover procedure according to the recognized handover type.

The radio resource reconfiguration message may be a handover command.

The information may include a C-RNT, a handover type indicator, aphysical cell identity (PCI), and a reconfiguration indicator. Thereconfiguration indicator may include a reconfiguration indicator of anRLC entity and that of a PDCP entity.

The first handover procedure may indicate a procedure for handoverbetween different base stations (intra Node B HO), and the secondhandover procedure may indicate a procedure for handover in the samebase station (inter Node B HO).

The UE may perform the first or second handover procedure based onwhether or not a new C-RNTI exists in the radio resource reconfigurationmessage.

The UE may perform the first or second handover procedure based onwhether or not a handover type indicator exists in the radio resourcereconfiguration message.

The UE may perform the first or second handover procedure based onwhether or not a new PCI exists in the radio resource reconfigurationmessage.

If a transmission/reception acknowledgement information operationindicator is included in the information, the UE may start datatransmission after receiving transmission/reception acknowledgementinformation. The transmission/reception acknowledgement information maybe a PDCP status PDU.

The embodiments of the present invention, the data transmission startpoint is adjusted according to the information included in the handovercommand and the radio resource reconfiguration operation is performedaccording to the type of handover, to thus minimize an unnecessaryoperation occurring in the handover process and optimizing a datatransmission between the UE and the base station.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a network structure of the E-UMTS, a mobile communicationsystem, applicable to the related art and the present invention;

FIG. 2 shows the layers of a control plane of a radio interfaceprotocol;

FIG. 3 shows the layers of a user plane of the radio interface protocol;

FIG. 4 is a signal flow chart illustrating a handover procedure betweena UE and a base station defined in the related art LTE;

FIG. 5 shows an example of an unnecessary data transmission occurring inthe handover procedure between the UE and the base station according tothe related art; and

FIG. 6 is a flow chart illustrating a method for processing a handoverprocedure in a mobile communication system according to an exemplaryembodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

The present invention is implemented in a mobile communication systemsuch as an LTE. However, without being limited thereto, the presentinvention can be also applicable to any communication system operatingaccording to different standards. The exemplary embodiments of thepresent invention will now be described in detail.

The present invention proposes that if a user equipment (UE) and a basestation are set to transmit/receiver transmission/receptionacknowledgement information to each other in a handover procedure, eachentity starts data transmission after receiving thetransmission/reception acknowledgement information.

Namely, when the UE receives a handover command from a source basestation, it performs connection to a target base station according tothe corresponding handover command, transmits a handover completemessage to the target base station, and waits reception of thetransmission/reception acknowledgement information from the target basestation. When the transmission/reception acknowledgement information isreceived, the UE recognizes a list of data to be retransmitted accordingto content of the transmission/reception acknowledgement information,and starts data transmission.

The transmission/reception acknowledgement information is a PDCP statusPDU.

The data to be retransmitted by the UE is a PDCP SDU.

The data to be retransmitted by the UE is a PDCP PDU.

Preferably, the handover command received from the source base stationinforms about an operation to be performed by the terminal in the targetbase station.

Namely, the handover command includes a transmission/receptionacknowledgement information operation indicator, and thetransmission/reception acknowledgement information operation indicatorindicates whether the UE should start data transmission to the targetbase station after receiving the transmission/reception acknowledgementinformation or whether the UE should immediately start data transmissionregardless of whether or not the transmission/reception acknowledgementinformation is received. Thus, when the transmission/receptionacknowledgement information operation indicator indicates, the UE waitsfor data transmission until it receives the transmission/receptionacknowledgement information from the target base station, and when thetransmission/reception acknowledgement information operation indicatordoes not indicate, the UE starts data transmission immediately when itsconnection to the target base station is completed.

The transmission/reception acknowledgement information operationindicator is informed by the target base station to the source basestation, and the source base station transmits it to the UE.

Preferably the transmission/reception acknowledgement informationoperation indicator indicates whether or not the target base stationshould transmit the transmission/reception acknowledgement informationto the UE.

As described above with respect to the above related art, when the UE isconnected to the target base station according to a handover process, itstarts data transmission immediately when the handover process issuccessfully performed. At this time, the UE transmits the otherremaining data than the data acknowledged for its reception, among datathe UE has transmitted, while remaining at the source base station, tothe target base station. And, when the UE additionally receivestransmission/reception acknowledgement information from the target basestation, the UE transmits only data notified to have not been receivedin the transmission/reception acknowledgement information. The UE doesnot transmit data which has been successfully received by the basestation in the transmission/reception acknowledgement information, anymore.

Preferably, while the UE is transmitted in the target base station, ifthe UE receives transmission/reception acknowledgement information fromthe base station with respect to the corresponding data, in particular,if the transmission/reception acknowledgement information indicates thatthe data has been successfully received, the UE does not transmit thedata any more. In particular, if a portion of the data has been alreadytransmitted to the base station, the UE performs a process of removingthe corresponding data.

For example, it is assumed that the UE transmits the PDCP SDUs 1, 2 and3 to the source base station and receives acknowledgement of only thePDCP SDU 1 from the source station, and handover occurs afterwards.

In this case, immediately when the UE is connected to the target basestation, it starts transmission of the PDCP SDU 2 and the PDCP SDU 3.The PDCP SDUs are delivered via the RLC entity. If thetransmission/reception acknowledgement information is receivedindicating that the PDCP SDU 2 has been properly received while the RLCentity transmits the PDCP SDUs, the PDCP entity of the UE determines notto transmit the PDCP SDU 2 any more and instructs the RLC entity todelete the PDCP SDU 2 or not to transmit the PDCP SDU 2 any more. Then,the RLC entity of the UE configures control information and transmits itto the RLC entity of the base station to inform that transmission of theRLC PDU or the RLC SDU with respect to the PDCP SDU 2 has been stoppedor does not occur any longer.

The present invention proposes that the UE perform a proper operationaccording to a type of handover.

To this end, the base station transmits a radio resource reconfigurationmessage to the UE, and the UE discriminates a first handover or a secondhandover based on mobility-related information included in the radioresource reconfiguration message, and performs the discriminatedhandover procedure.

Preferably, the radio resource reconfiguration message indicates ahandover command.

Preferably, the first handover indicates handover between different basestations (intra Node B HO), and the second handover indicates a handoverwithin the same base station (inter Node B HO).

Preferably, the mobility-related information includes a C-RNT, ahandover type indicator, a physical cell ID (PCI), and a reconfigurationindicator. The reconfiguration indicator includes a reconfigurationindicator of the RLC entity or a reconfiguration indicator of the PDCPentity.

FIG. 6 is a flow chart illustrating a method for processing a handoverprocedure in a mobile communication system according to an exemplaryembodiment of the present invention.

As shown in FIG. 6, when a radio resource reconfiguration message (e.g.,handover command) is received from the base station (S100), the UEsearches information (e.g., mobility-related information) included inthe radio resource reconfiguration message (S101).

The UE recognizes a type of handover, namely, whether or not thecurrently performed handover is first or second handover, based on thesearched information (S102, S103).

For example, if the radio resource reconfiguration message includes aC-RNTI and the corresponding C-RNTI is a new C-RNTI different from thatused in a source cell, the UE regards the handover as first handover.

If the radio resource reconfiguration message includes a handover typeindicator, the UE recognizes first or second handover according towhether or not the corresponding handover type indicator indicates theintra Node B HO or the inter Node B HO.

If the radio resource reconfiguration message includes the PCI and thecorresponding PCI is a new PCI different from that used in the sourcecell, the UE recognizes the handover as the first handover.

Finally, if the radio resource reconfiguration message includes thereconfiguration indicator, the UE recognizes the handover as the firsthandover, or otherwise, the UE recognizes the handover as the secondhandover. The reconfiguration indicator is that of the RLC entity or thePDCP entity.

Accordingly, when the type of the handover is discriminated, the UEdifferent performs radio resource reconfiguration operation according tothe first handover or the second handover.

Namely, when the information included in the radio resourcereconfiguration message indicates the first handover, the UEreconfigures the PDCP entity and the RLC entity when entering a new cell(S104). In particular, when the PDCP entity is reconfigured, the UEtransmits the PDCP status PDU.

If the mobility-related information included in the radio resourcereconfiguration message indicates the second handover, the UE does notreconfigure the PDCP entity and the RLC entity when entering the newcell (S105). Namely, the UE uses the same RLC entity and the same PDCPentity before and after the handover, and the status information of theRLC and the PDCP are maintained.

The radio resource reconfiguration message, namely, the handovercommand, transmitted by the base station to the UE may includeinformation (RLC reconfiguration indicator or PDCP reconfigurationindicator) indicating whether the UE should reconfigure the RLC entityor the PDCP entity. Thus, only when the reconfiguration indicator of theRLC entity indicates reconfiguration, the UE reconfigures the RLCentity, and only when the reconfiguration indicator of the PDCP entityindicates reconfiguration, the UE reconfigures the PDCP entity.

As so far described, according to the embodiments of the presentinvention, the data transmission start point is adjusted according tothe information included in the handover command and the radio resourcereconfiguration operation is performed according to the type ofhandover, to thus minimize an unnecessary operation occurring in thehandover process and optimizing a data transmission between the UE andthe base station.

Meanwhile, the method according to the present invention, as describedso far, can be implemented by hardware or software, or any combinationthereof. For example, the method according to the present invention maybe stored in a storage medium (e.g., an internal memory of a mobileterminal, a flash memory, a hard disc, etc.). Alternatively, the methodaccording to the present invention can be implemented as codes orcommand words within a software program capable of being executed by aprocessor (e.g., a microprocessor in a mobile terminal).

The present invention has been explained with reference to theembodiments which are merely exemplary. It will be apparent to thoseskilled in the art that various modifications and equivalent otherembodiments can be made in the present invention without departing fromthe spirit or scope of the invention. Also, it will be understood thatthe present invention can be implemented by selectively combining theaforementioned embodiment(s) entirely or partially. Thus, it is intendedthat the present invention cover modifications and variations of thisinvention provided they come within the scope of the appended claims andtheir equivalents.

The invention claimed is:
 1. A method for processing a handoverprocedure by a user equipment (UE) of a mobile communication system, themethod comprising: receiving, by the UE, a radio resourcereconfiguration message from a base station; recognizing, by the UE, ahandover type based on information included in the received radioresource reconfiguration message, wherein the information is mobilityrelated information, wherein the mobility related information includeseach of a first parameter indicating a target physical cell identity anda second parameter indicating a new user equipment (UE) identity, andwherein the first parameter is a physical cell identity (PCI) and thesecond parameter is a cell-radio network temporary identifier (C-RNTI);and performing, by the UE, a first or second handover procedureaccording to the recognized handover type, wherein the first or secondhandover procedure is performed based on whether a new C-RNTI or a newPCI exists in the radio resource reconfiguration message.
 2. The methodof claim 1, wherein the radio resource reconfiguration message is ahandover command.
 3. The method of claim 1, wherein the informationfurther comprises a handover type indicator.
 4. The method of claim 1,wherein the first handover procedure indicates a procedure for handoverbetween different base stations.
 5. The method of claim 1, wherein thesecond handover procedure indicates a procedure for handover in the samebase station.
 6. The method of claim 1, further comprising: if atransmission/reception acknowledgement information operation indicatoris included in the information, starting data transmission afterreceiving transmission/reception acknowledgement information.
 7. Themethod of claim 6, wherein the transmission/reception acknowledgementinformation is a packet data convergence protocol (PDCP) status protocoldata unit (PDU).
 8. A mobile communication system, comprising: a basestation configured to transmit a radio resource reconfiguration message;and a user equipment (UE) configured to receive the radio resourcereconfiguration message, recognize a handover type based on informationincluded in the received radio resource reconfiguration message, andperform a first or second handover procedure according to the recognizedhandover type, wherein the information is mobility related information,wherein the mobility related information includes each of a firstparameter indicating a target physical cell identity and a secondparameter indicating a new user equipment (UE) identity, wherein thefirst parameter is a physical cell identity (PCI) and the secondparameter is a cell-radio network temporary identifier (C-RNTI), andwherein the UE performs the first or second handover procedure based onwhether a new C-RNTI or a new PCI exists in the radio resourcereconfiguration message.
 9. The system of claim 8, wherein the radioresource reconfiguration message is a handover command.
 10. The systemof claim 8, wherein the information further comprises a handover typeindicator.
 11. The system of claim 8, wherein the first handoverprocedure indicates a procedure for handover between different basestations, and the second handover procedure indicates a procedure forhandover within the same base station.
 12. The system of claim 8,wherein if a transmission/reception acknowledgement informationoperation indicator is included in the information, the UE starts datatransmission after receiving transmission/reception acknowledgementinformation.
 13. The system of claim 12, wherein thetransmission/reception acknowledgement information comprises a packetdata convergence protocol (PDCP) status protocol data unit (PDU).
 14. Auser equipment configured to operate in a mobile communication system,the user equipment comprising: a processor configured to receive a radioresource reconfiguration message from a base station, recognize ahandover type based on information included in the received radioresource reconfiguration message, and perform a first or second handoverprocedure according to the recognized handover type, wherein theinformation is mobility related information, wherein the mobilityrelated information includes each of a first parameter indicating atarget physical cell identity and a second parameter indicating a newuser equipment (UE) identity, wherein the first parameter is a physicalcell identity (PCI) and the second parameter is a cell-radio networktemporary identifier (C-RNTI), and wherein the first or second handoverprocedure is performed based on whether a new C-RNTI or a new PCI existsin the radio resource reconfiguration message.